Method for transmitting data and terminal device

ABSTRACT

Implementations of the present disclosure relate to a method for transmitting data and a terminal device. The method includes: if there is an untransmitted first MAC PDU in a target HARQ process, sending a third MAC PDU to a physical layer at an MAC layer, wherein, a first resource corresponding to the first MAC PDU overlaps with a second resource corresponding to a second MAC PDU, the third MAC PDU includes data in the first MAC PDU, and the physical layer is used for transmitting the third MAC PDU through a third resource.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation application of International PCTApplication No. PCT/CN2019/080240 filed on Mar. 28, 2019, the entirecontent of which is hereby incorporated by reference.

TECHNICAL FIELD

The present disclosure relates to the field of communication, inparticular to a method for transmitting data and a terminal device.

BACKGROUND

In a 5G system, according to business requirements, it may be dividedinto three main application scenarios, which are respectively Enhancedmobile broadband (eMBB), Massive Machine Type Communications (mMTC) andUltra reliability and low latency communication (uRLLC).

In the uRLLC scenario, due to existence of such a service withrequirements on high reliability and low latency, a base station mayschedule an uplink (UL) grant for an eMBB service, and then schedule anUL grant for the uRLLC, wherein the two grants partially overlap intime. Or, after the base station may schedule an UL grant for an uRLLCservice, and then schedule an UL grant for another uRLLC with adifferent Quality of Service (QoS) requirement, wherein the two grantspartially overlap in time. In addition, for the above scenario, twogrants with overlapping parts in time may also be resources configuredby the base station, such as configured grants.

At this time, an MAC entity may assemble each grant, but finally onlyone grant is to be transmitted to an opposite entity, for example, auser equipment only transmits one grant to a network side. That is, atthis time, at a same time point, a Media Access Control (MAC) entityconstitutes and generates two MAC Protocol Data Units (PDUs) for the twogrants respectively, such as MAC PDU 1 and MAC PDU 2, which mayrespectively correspond to a Hybrid Automatic Repeat reQuest (HARQ)process 1 and a HARQ process 2. However, only one MAC PDU istransmitted, for example, the MAC PDU 2 and its corresponding HARQprocess 2 are transmitted. The MAC entity, however, may not know whichMAC PDU or grant is finally to be transmitted.

When a new transmission is scheduled later on the network side, or thereis a configured grant which has a corresponding process number, process1, since in the process there is MAC PDU 1 which is assembled but hasnot been sent, how to identify this scenario and how to deal with thisscenario are currently unsolved problems.

SUMMARY

The present disclosure provides a method for transmitting data and aterminal device.

In a first aspect, a method for transmitting data is provided,including: sending a third MAC PDU to a physical layer at an MAC layer,if there is an untransmitted first MAC PDU in a target HARQ process,wherein a first resource corresponding to the first MAC PDU overlapswith a second resource corresponding to a second MAC PDU, the third MACPDU includes data in the first MAC PDU, and the physical layer is usedfor transmitting the third MAC PDU through a third resource.

In a second aspect, a method for transmitting data is provided,including: sending a third MAC PDU to a physical layer at an MAC layer,if there is an untransmitted first MAC PDU in a target HARQ process,wherein the physical layer is used for transmitting the third MAC PDUthrough a third resource, wherein, a first resource corresponding to thefirst MAC PDU overlaps with a second resource corresponding to a secondMAC PDU, a configured grant timer corresponding to the target HARQprocess is running, and the third MAC PDU does not include data in thefirst MAC PDU.

In a third aspect, a terminal device is provided, configured to performthe method in any one of the above first to second aspects or in eachimplementation thereof. Specifically, the terminal device includesfunctional modules configured to perform the method in any one of theabove first to second aspects or in each implementation thereof.

In a fourth aspect, a chip is provided, configured to implement themethod in any one of the above first to second aspects or in eachimplementation thereof. Specifically, the chip includes a processor,configured to call and run a computer program from a memory, such that adevice on which the chip is installed performs the method in any one ofthe above first to second aspects or in each implementation thereof.

In a fifth aspect, a computer-readable storage medium is provided,configured to store a computer program that causes a computer to performthe method in any one of the above first to second aspects or in eachimplementation thereof.

In a sixth aspect, a computer program product is provided, includingcomputer program instructions that cause a computer to perform themethod in any one of the above first to second aspects or in eachimplementation thereof.

In a seventh aspect, a computer program is provided, causing, when beingrun on a computer, a computer to perform the method in any one of theabove first to second aspects or in each implementation thereof.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic diagram of architecture of a communication systemaccording to an implementation of the present disclosure.

FIG. 2 is a schematic diagram of a scenario of resource conflictaccording to an implementation of the present disclosure.

FIG. 3 is a schematic flowchart of a method for transmitting dataaccording to an implementation of the present disclosure.

FIG. 4 is a schematic diagram of another scenario of resource conflictaccording to an implementation of the present disclosure.

FIG. 5 is a schematic flowchart of another method for transmitting dataaccording to an implementation of the present disclosure.

FIG. 6 is a schematic block diagram of a terminal device according to animplementation of the present disclosure.

FIG. 7 is a schematic block diagram of a communication device accordingto an implementation of the present disclosure.

FIG. 8 is a schematic block diagram of a chip according to animplementation of the present disclosure.

FIG. 9 is a schematic diagram of a communication system according to animplementation of the present disclosure.

DETAILED DESCRIPTION

Technical solutions in implementations of the present disclosure will bedescribed below with reference to the drawings in implementations of thepresent disclosure. It is apparent that the implementations describedare a part of implementations of the present disclosure, but not allimplementations of the present disclosure. According to theimplementations of the present disclosure, all other implementationsobtained by a person of ordinary skill in the art without paying aninventive effort are within the protection scope of the presentdisclosure.

The technical solutions of the implementations of the present disclosuremay be applied to various communication systems, such as a Global Systemof Mobile communication (GSM) system, a Code Division Multiple Access(CDMA) system, a Wideband Code Division Multiple Access (WCDMA) system,a General Packet Radio Service (GPRS), a Long Term Evolution (LTE)system, an LTE Frequency Division Duplex (FDD) system, an LTE TimeDivision Duplex (TDD) system, a Universal Mobile TelecommunicationSystem (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX)communication system, or a 5G system, etc.

Illustratively, a communication system 100 applied in an implementationof the present disclosure is shown in FIG. 1. The communication system100 may include a network device 110, and the network device 110 may bea device that communicates with a terminal device 120 (or referred to asa communication terminal, or a terminal). The network device 110 mayprovide communication coverage for a specific geographical area, and maycommunicate with terminal devices located within the coverage area.Optionally, the network device 110 may be a Base Transceiver Station(BTS) in a GSM system or a CDMA system, a NodeB (NB) in a WCDMA system,an Evolutional Node B (eNB or eNodeB) in an LTE system, or a radiocontroller in a Cloud Radio Access Network (CRAN), or the network devicemay be a network side device in a mobile switch center, a relay station,an access point, a vehicle-mounted device, a wearable device, a hub, aswitch, a bridge, a router, or a 5G network, or a network device in afuture evolved Public Land Mobile Network (PLMN), etc. The communicationsystem 100 also includes at least one terminal device 120 located withina coverage range of the network device 110. As used herein, the term“terminal device” includes, but not limited to, an apparatus configuredto receive/send a communication signal via a wired circuit connection,for example, via Public Switched Telephone Networks (PSTN), a DigitalSubscriber Line (DSL), a digital cable, a direct cable connection;and/or another data connection/network; and/or via a wireless interface,for instance, for a cellular network, a Wireless Local Area Network(WLAN), a digital television network such as a DVB-H network, asatellite network, or an AM-FM broadcast sender; and/or another terminaldevice; and/or an Internet of Things (IoT) device. A terminal deviceconfigured to communicate via a wireless interface may be referred to asa “wireless communication terminal”, a “wireless terminal” or a “mobileterminal”. Examples of the mobile terminal include, but not limited to,a satellite or cellular telephone, a Personal Communication System (PCS)terminal which may combine a cellular radio telephone and dataprocessing, faxing, and data communication abilities, a Personal DigitalAssistant (PDA) that may include a radio telephone, a pager, anInternet/intranet access, a Web browser, a memo pad, a calendar, and/ora Global Positioning System (GPS) receiver, and a conventional laptopand/or palmtop receiver or another electronic apparatus including aradio telephone transceiver. The terminal device may be referred to asan access terminal, a User Equipment (UE), a subscriber unit, asubscriber station, a mobile station, a mobile platform, a remotestation, a remote terminal, a mobile device, a user terminal, aterminal, a wireless communication device, a user agent, or a userapparatus. The access terminal may be a cellular phone, a cordlessphone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop(WLL) station, a Personal Digital Assistant (PDA), a handheld devicewith a wireless communication function, a computing device, or anotherprocessing device connected to a wireless modem, a vehicle-mounteddevice, a wearable device, a terminal device in a 5G network, or aterminal device in a future evolved PLMN, or the like.

Optionally, a Device to Device (D2D) communication may be performedbetween the terminal devices 120.

Optionally, the 5G system or the 5G network may also be referred to as aNew Radio (NR) system or an NR network.

FIG. 1 shows one network device and two terminal devices as an example.Optionally, the communication system 100 may include multiple networkdevices, and another quantity of terminal devices may be included withina coverage range of each network device, which is not limited in theimplementations of the present disclosure.

Optionally, the communication system 100 may also include anothernetwork entity such as a network controller, a mobile management entity,or the like, which is not limited in the implementations of the presentdisclosure.

It should be understood that, a device with a communication function ina network/system in the implementation of the present disclosure may bereferred to as a communication device. Taking the communication system100 shown in FIG. 1 as an example, the communication device may includea network device 110 and a terminal device 120 which have communicationfunctions, and the network device 110 and the terminal device 120 may bethe specific devices described above, which will not be repeated here.The terminal device may also include another device in the communicationsystem 100, e.g., another network entity such as a network controller, amobile management entity, or the like, which is not limited in theimplementations of the present disclosure.

It should be understood that the terms “system” and “network” may oftenbe used interchangeably in this document. The term “and/or” in thisdocument is merely an association relation describing associatedobjects, indicating that there may be three relations, for example, Aand/or B may indicate three cases: A alone, both A and B, and B alone.In addition, the symbol “/” in this document generally indicates thatobjects before and after the symbol “/” have an “or” relation.

In an uRLLC topic of Release 15 of a 5G system, services with highreliability and low latency are taken into consideration and dealt with.In Release 16 (Rel-16), research objects were expanded, and researcheson Factory automation, Transport Industry and Electrical PowerDistribution were extended to the topic of 5G Industrial Internet ofThings (IIoT). Thus a concept of Time sensitive network (TSN) isintroduced. Finally, in the IIoT item, following several objects areconsidered: 1. TSN network-related enhancement; 2. priority withinusers; 3. Data duplication and multi-connectivity.

In conventional NR and LTE systems, for uplink dynamic scheduling, onlyone UL grant would be transmitted to a UE at a same time point. Whenthere is a conflict between a dynamic scheduling resource and aconfigured grant resource, it is usually preferred to dynamicallyschedule transmission. At this time, selection of a priority may bedetermined by an MAC layer (i.e., MAC entity), and the MAC layer mayselect one of two grant resources, and only assemble the MAC PDU for theone grant.

However, under the sub-topic of priority within users, several possibleexisting scenarios of resource conflicts are determined, taking uplinktransmission resources as an example, e.g., there are a conflict betweena configured grant and a configured grant, a conflict between a dynamicgrant and a dynamic grant, and a conflict between a dynamic grant and aconfigured grant.

Different scenarios correspond to different transmission requirements,such as dealing with a scenario with coexistence of multiple servicetypes (such as coexistence of the eMBB and the uRLLC); or a scenariowith coexistence of services of a same service type which have differentcharacteristics (such as coexistence of uRLLC service 1 and uRLLCservice 2 whose requirements on period latency are different); or thatused for realizing service transmission with high reliability and lowlatency (for example multiple types of configured grants are configuredfor use in a same uRLLC service, such that there is an available grantresource at any time point to ensure timely transmission of uRLLCservices).

However, in the uRLLC scenario, due to the existence of such a servicerequiring high reliability and low latency, the base station mayschedule an UL grant for the uRLLC after scheduling an UL grant for theeMBB service, and two grants overlap in time. Or, the base station mayschedule an UL grant for another uRLLC with a different QoS requirementafter scheduling an UL grant of the uRLLC service, and two grantsoverlap in time. At this time, the MAC entity may assemble each grant,but only one grant is to be transmitted to an opposite entity finally,for example, the UE only transmits one grant to the network side. Thatis, at this time, at a same time point, the MAC entity constitutes andgenerates two MAC PDUs for the two grants, such as MAC PDU 1 and MAC PDU2, which may correspond to Hybrid Automatic Repeat reQuest (HARQ)process 1 and HARQ process 2, respectively. However, only one MAC PDU istransmitted out, for example, the MAC PDU 2 and its corresponding HARQprocess 2 are transmitted. The MAC entity, however, may not know whichMAC PDU or grant is to be transmitted finally. In addition, for theabove scenario, two grants with overlapping parts in time may also beresources configured by the base station, such as configured grants.

When a new transmission is scheduled later on the network side, or thereis a configured grant which has a corresponding process number, process1, since in the process there is MAC PDU 1 which is assembled but hasnot been sent, how to identify this scenario and how to deal with thisscenario are a currently unsolved problem. If this untransmitted MAC PDUis directly discarded, it is very likely to cause a large number ofservices that should be transmitted to be discarded, which leads to aproblem that the QoS of the services cannot be met and the useexperience of services of the UE is reduced. For example, the uRLLCservice 2 is in unacknowledged mode (UM), and MAC PDUs assembled at theMAC layer are directly lost, which will cause that the data cannot berecovered, QoS cannot be met, and survival time cannot be ensured. Forexample, if the former and the latter packets are both lost, thetransmission of services will go wrong.

For example, FIG. 2 shows a schematic diagram of a scenario of aresource conflict in an implementation of the present disclosure. Asshown in FIG. 2, it is assumed that the network device sends any onepiece of Downlink Control Information (DCI) to the terminal device, forexample, DCI 1, wherein the DCI 1 indicates resource 1; and in addition,a same network device or different network device also send DCI 2 to theterminal device, wherein the DCI 2 is used for indicating resource 2.The MAC layer generates MAC PDU 1 and MAC PDU 2 corresponding to theresource 1 and the resource 2 respectively, wherein the MAC PDU 1corresponds to the resource 1 and the MAC PDU 2 corresponds to theresource 2. However, there is overlap between the resource 1 and theresource 2 in time domain and/or frequency domain. For example, as shownin FIG. 2, the terminal device may only send one of the MAC PDUs. Forexample, the terminal device only sends the MAC PDU 2, then how to dealwith such scenario is a problem to be solved urgently at present. Forexample, how to deal with the MAC PDU 1 and the MAC layer does not knowwhich MAC PDU is sent, and how to deal with the HARQ process or the MACPDU 1 if a new transmission is scheduled later on the network side, orif there is a configured grant which has a corresponding process numberidentical to that of the MAC PDU 1 that has not been sent.

In addition, there is also a special restrictive condition of timercorresponding to the configured grant. Specifically, for a case that thegrant is a configured grant, generally the MAC entity will only indicatethe HARQ entity to use the configured grant for transmission if acorresponding configured Grant Timer is not running. That is, for eachconfigured grant in each serving cell, if the configured grant isconfigured and activated, the MAC entity will perform following acts: ifthere is no overlap between a duration of a Physical Uplink SharedChannel (PUSCH) of a configured uplink grant and a PUSCH durationresource indicated by a Physical Downlink Control Channel (PDCCH) or aRandom Access response (RAR), the HARQ process ID is set as the HARQprocess ID associated with this PUSCH duration. Further, in a case thatthe configured Grant Timer of the HARQ process is not running, it isdetermined that a New Data Indication (NDI) bit of the correspondingHARQ process is flipped, and the configured UL grant and thecorresponding HARQ information are delivered to a HARQ entity in the MAClayer.

However, if the PUSCH duration of the configured uplink grant overlapswith the PUSCH duration resource indicated by the PDCCH or RAR, the MAClayer generates two MAC PDUs for the two grants respectively, and onlyone MAC PDU can be transmitted, so how to deal with the untransmittedMAC PDU or the HARQ process corresponding to the untransmitted MAC PDUis also a problem to be solved urgently at present.

Therefore, an implementation of the present disclosure proposes a methodfor transmitting data which can be applied to the above scenarios ofresource conflicts, solving a problem of how the MAC entity deals withan untransmitted MAC PDU, clarifying processing behavior of a UE, andensuring integrity of protocol flow processing, and can avoidunnecessary packet loss.

FIG. 3 is a schematic flowchart of a method for transmitting data 200according to an implementation of the present disclosure. The method 200may be performed by a terminal device, for example, the terminal devicemay be the terminal device shown in FIG. 1. Specifically, the method 200may be performed by an MAC entity included in the terminal device, inother words, the method 200 may be performed at an MAC layer of theterminal device. Specifically, as shown in FIG. 3, the method 200includes: S210, if there is an untransmitted first MAC PDU in a targetHARQ process, a third MAC PDU is sent to a physical layer at an MAClayer, wherein a first resource corresponding to the first MAC PDUoverlaps with a second resource corresponding to a second MAC PDU, andthe third MAC PDU includes data in the first MAC PDU, and the physicallayer is used for transmitting the third MAC PDU through the thirdresource.

It should be understood that the resource in the implementation of thepresent disclosure may refer to a grant, or a Uplink Shared Channel(UL-SCH), or a PUSCH, wherein the resource includes the first resource,the second resource and the third resource.

It should be understood that the first resource corresponding to thefirst MAC PDU in implementations of the present disclosure may be adynamic scheduling resource or a configured grant resource, that is, thefirst resource may be a dynamic grant or a configured grant. Inaddition, the first resource may refer to a time domain and/or frequencydomain resource of any size; and the first resource may refer to acontinuous or a discontinuous resource, which is not limited in theimplementations of the present disclosure.

Similarly, the second resource corresponding to the second MAC PDU inimplementations of the present disclosure may also be a dynamic grant ora configured grant. In addition, the second resource may also refer to atime domain and/or frequency domain resource of any size; and the secondresource may refer to a continuous or discontinuous resource.

Similarly, the third resource in implementations of the presentdisclosure may also be a dynamic grant or a configured grant. Inaddition, the third resource may also refer to a time domain and/orfrequency domain resource of any size; and the third resource may referto a continuous or discontinuous resource.

In addition, the first resource overlaps with the second resource, whichmay mean that the first resource and the second resource partiallyoverlap or completely overlap in the time domain and/or the frequencydomain.

In an implementation of the present disclosure, the method 200 mayfurther include: the first MAC PDU and the second MAC PDU are generatedat the MAC layer, wherein the first MAC PDU corresponds to the firstresource and the second MAC PDU corresponds to the second resource.Therefore, due to a conflict between the first resource and the secondresource, the terminal device can only choose to send one of the firstMAC PDU and the second MAC PDU to a receiving end (e.g., networkdevice). Here, assuming that the second MAC PDU is sent to the receivingend, the method 200 further includes: the second MAC PDU is sent to thephysical layer at the MAC layer, such that the physical layer transmitsthe second MAC PDU through the second resource; but for the first MACPDU, the MAC layer may not send the first MAC PDU to the physical layer,or, the method 200 may further include that the first MAC PDU is sent tothe physical layer at the MAC layer, but the physical layer does notsend the second MAC PDU due to the conflict between the first resourceand the second resource.

At this time, if the network side schedules a new transmission later, orthere is a configured grant, that is, the terminal device determines thethird resource, wherein the third resource may be a dynamic grant or aconfigured grant, then the third MAC PDU may be sent to the physicallayer at the MAC layer, such that the physical layer transmits the thirdMAC PDU through the third resource. Herein, the third MAC PDU includesdata in the first MAC PDU. For example, the data in the first MAC PDUmay include an MAC SDU in the first MAC PDU, that is, the third MAC PDUincludes the MAC SDU in the first MAC PDU. Optionally, the third MAC PDUmay also include a MAC CE in the first MAC PDU.

For example, FIG. 4 shows a schematic diagram of a scenario of aresource conflict according to an implementation of the presentdisclosure. As shown in FIG. 4, it is assumed that the first resource isindicated by the network device through DCI 1 and the first resourcecorresponds to HARQ process 1, and the second resource is indicated bythe network device through DCI 2 and the second resource corresponds toHARQ process 2. The MAC layer of the terminal device generates MAC PDU1, which corresponding to that a resource 1 needs to be occupied, andgenerates MAC PDU 2, which corresponding to that a resource 2 needs tobe occupied. However, since the resource 1 overlaps with the resource 2,for example, they overlap as shown in FIG. 2, here, assuming that theterminal device chooses to send MAC PDU 2, then there is an unsent MACPDU 1 in HARQ process 1, that is, the HARQ process 1 is a target HARQprocess in the implementation of the present disclosure, and there is anunsent first MAC PDU, i.e. MAC PDU 1 in the target HARQ. At this time,the terminal device receives DCI 3 sent by the network device, and theDCI 3 indicates a resource 3, and the resource 3 also corresponds to theHARQ process 1, but there is still an unsent MAC PDU 1 in the HARQprocess 1, then the terminal device may send MAC PDU 3 through theresource 3, wherein the MAC PDU 3 includes the MAC SDU in the MAC PDU 1.Optionally, the MAC PDU3 may also include the MAC CE in MAC PDU 1.

It should be understood that in the implementation of the presentdisclosure, the data of the first MAC PDU included in the third MAC PDUmay include the MAC SDU in the first MAC PDU, that is, the third MAC PDUincludes the MAC SDU in the first MAC PDU. For example, the third MACPDU may be obtained after the first MAC PDU is reassembled, for example,the third MAC PDU is obtained after the MAC SDU in the first MAC PDU isreassembled with another MAC SDU; for example, the third MAC PDU may beobtained after the first MAC PDU is reassembled, for example, the thirdMAC PDU is obtained after the MAC SDU in the first MAC PDU isreassembled with padding; or, the third MAC PDU may also be the firstMAC PDU, that is, the first MAC PDU and the third MAC PDU are the sameMAC PDU; or, the third MAC PDU may also include the first MAC PDU and apadding bit, which is not limited in the implementation of the presentdisclosure. Furthermore, if there is reassembly, the MAC layer needs toindicate a Multiplexing and assembly entity to contain the data of thefirst MAC PDU, such as the MAC SDU, in the third MAC PDU or atransmission of the third resource. Further, the MAC layer acquires thethird MAC PDU from the Multiplexing and assembly entity.

In following, how to send the third MAC PDU in different scenarios willbe described in detail with reference to several specificimplementations.

Optionally, as an implementation, the third MAC PDU includes the MAC SDUin the first MAC PDU, which may mean that the third MAC PDU is obtained,after the MAC layer reassembles the first MAC PDU. Specifically, thethird MAC PDU may be obtained, after the MAC layer reassembles the firstMAC PDU through an MAC Multiplexing and assembly entity. For example,after the Multiplexing and assembly entity reassembles the first MACPDU, the third MAC PDU is obtained, wherein the third MAC PDU mayinclude at least one MAC subPDU, and the at least one MAC sub PDUcarries the MAC SDU in the first MAC PDU acquired from the target HARQprocess.

In the present implementation, the terminal device may obtain the thirdMAC PDU after the MAC layer reassembles the first MAC PDU, in a casethat a first condition is met. Herein, the first condition includes atleast one of following conditions: a size of the third resource does notmatch a size of the first MAC PDU; according to a first Transport Block(TB) in the target HARQ process, it is determined that a New DataIndication (NDI) corresponding to the target HARQ process is flipped,wherein the first TB corresponds to the first resource; there is theuntransmitted first MAC PDU in the target HARQ process; the firstresource corresponding to the first MAC PDU which exists in the targetHARQ process is not transmitted; the first resource overlaps with thesecond resource; the NDI corresponding to the target HARQ process isflipped; the first TB in the target HARQ process is not transmitted;indication information sent by the physical layer is received at the MAClayer, wherein the indication information indicates that the first MACPDU in the target HARQ process is not transmitted; the first resourceand/or the third resource are configured grant resources; a configuredgrant timer corresponding to the target HARQ process is running; apriority of the third resource is higher than a priority of the firstresource; the third resource is a preemption resource; a priority of thesecond resource is higher than the priority of the first resource; thesecond resource is transmitted prior to the first resource; and a HARQprocess number corresponding to the first resource and a HARQ processnumber corresponding to the third resource are same.

Herein, for the case that the first condition includes that the size ofthe third resource does not match the size of the first MAC PDU, forexample, the size of the third resource is larger than that of the firstMAC PDU, then after the MAC SDU in the first MAC PDU may be reassembledwith another MAC SDU at the MAC layer, it may be transmitted through thethird resource. For another example, the size of the third resource islarger than that of the first MAC PDU, then after the MAC SDU in thefirst MAC PDU may be reassembled with the MAC CE at the MAC layer, itmay be transmitted through the third resource. For another example, thesize of the third resource is larger than that of the first MAC PDU,then after the MAC SDU in the first MAC PDU may be reassembled withpadding at the MAC layer, it may be transmitted through the thirdresource. Or, the reassembly may be made by any combination of theseseveral modes, and then transmission is made through the third resource.In this way, the third resource may also be fully utilized to avoidwaste of a resource.

For the case that the first condition includes that the terminal devicedetermines that the NDI corresponding to the target HARQ process isflipped, for example, it may be determined whether the NDI correspondingto the target HARQ process is flipped according to the first TB in thetarget HARQ process, wherein the first TB corresponds to the firstresource. Specifically, if the NDI is flipped, it means that the thirdresource is used for transmitting new data instead of retransmittingdata, then the third MAC PDU including the data in the first MAC PDU maybe transmitted through the third resource. Contrary to this case, if theNDI is not flipped, it means that the third resource is used fortransmitting retransmission data, and the terminal device may determinewhether to send the third MAC PDU according to another condition in thefirst condition, or, the terminal device may send retransmission datacorresponding to the third resource without reassembling the first MACPDU through the Multiplexing and assembly entity, but theimplementations of the present disclosure are not limited thereto.

For the case that the first condition includes determining that there isthe untransmitted first MAC PDU in the target HARQ process, the MAClayer of the terminal device may determine whether there is theuntransmitted first MAC PDU in the target HARQ process in various modes.For example, the MAC layer may determine that there is the untransmittedfirst MAC PDU in the target HARQ process by interacting with thephysical layer, for example, the first condition may include receivingindication information sent by the physical layer at the MAC layer,wherein the indication information indicates that the first MAC PDU inthe target HARQ process is not transmitted.

For another example, the MAC layer may also determine that there is theuntransmitted first MAC PDU in the target HARQ process by a preset rule.For example, if the first resource of the first MAC PDU conflicts withthe second resource of the second MAC PDU, and the preset rule indicatesthat only MAC PDU that the time domain is on the latter is sent, thenthe MAC layer may determine that the first MAC PDU that the time domainis on former exists in the target HARQ process and has not beentransmitted. For another example, if the first resource of the first MACPDU conflicts with the second resource of the second MAC PDU, the MAClayer determines the MAC PDU not to be sent according to a grantattribute. For another example, if the first resource of the first MACPDU conflicts with the second resource of the second MAC PDU, the MACdetermines which grant to be sent and further determines the unsent MACPDU. For another example, the MAC layer may determine which one of thefirst MAC PDU and the second MAC PDU to be sent, that is, the MAC layerdetermines to send the second MAC PDU instead of the first MAC PDU, thenthe MAC layer may determine that there is the first MAC PDU that has notbeen transmitted in the target HARQ process, but the implementations ofthe present disclosure are not limited thereto.

Similar to determining that there is the untransmitted first MAC PDU inthe target HARQ process, the first condition may also includedetermining that the first resource corresponding to the first MAC PDUexisting in the target HARQ process is not transmitted, and/or, thefirst condition may also include that the first TB in the target HARQprocess is not transmitted.

For a case that the first condition includes that the first resourceoverlaps with the second resource, that is, the first resource is aconflicted or overlapped resource; or, it may also be described as: thefirst TB overlaps or conflicts with the second TB, that is, the first TBis conflicted or overlapped, wherein the first TB corresponds to thefirst MAC PDU and the second TB corresponds to the second MAC PDU, thatis, the first TB occupies the first resource and the second TB occupiesthe second resource; or, it may also be described as: the transmissionof the first TB conflicts or overlaps with the transmission of thesecond TB, that is, the transmission of the first TB is conflicted oroverlapped, but the implementations of the present disclosure are notlimited thereto.

For a case that the first condition includes that the configured granttimer corresponding to the target HARQ process is running, generally, ifthe first resource is a configuration grant resource and/or the thirdresource is a configuration grant resource, the configured grant timercorresponding to the target HARQ process may be running; or, in a casethat the first resource or the third resource is a dynamic schedulingresource, the configured grant timer corresponding to the target HARQprocess may also be running. Specifically, if the configured grant timercorresponding to the target HARQ process is running, combined withanother condition in the first condition, for example, for a case thatthere is the first MAC PDU untransmitted in the target HARQ process, orthere is an assembled first MAC PDU in the target HARQ process, whilethe first resource corresponding to the first MAC PDU is nottransmitted, then the MAC layer may still send the third resource andrelated information of the target HARQ to the HARQ entity, such that theHARQ entity sends the third MAC PDU to the physical layer, such that thephysical layer sends the third MAC PDU through the third resource.

For a case that the first condition includes that the priority of thethird resource is higher than that of the first resource, for example,the third resource may be a preemption resource. For a case that thefirst condition includes that the second resource is transmitted priorto the first resource, for example, the priority of the second resourcemay be higher than that of the first resource. Because the firstresource conflicts with the second resource, and the second resource istransmitted preferentially, the first resource is not transmitted,resulting in that there is an untransmitted first MAC PDU in the targetHARQ process. For a case that the first condition includes that the HARQprocess number corresponding to the first resource and the HARQ processnumber corresponding to the third resource are same, it may bedetermined to use the third resource to transmit the third MAC PDU whichincludes the data in the first MAC PDU in combination with anothercondition in the first condition.

Optionally, the first condition may also include: if the HARQ processesof the first MAC PDU and the second MAC PDU are same, then in a timeorder, the former MAC PDU may be reserved and the other MAC PDU may besent. For example, the former MAC PDU is the first MAC PDU, then thesecond MAC PDU is sent. Contrary to this case, if the HARQ processes ofthe first MAC PDU and the second MAC PDU are same, then in a time order,the former MAC PDU may be flushed and the latter MAC PDU may be sent.For example, if the former MAC PDU is the first MAC PDU, then the lattersecond MAC PDU is sent and the first MAC PDU is flushed. At this time,in the corresponding HARQ process there is no MAC PDU which is not sent.

Similarly, the first condition may also include: if the HARQ processesof the first MAC PDU and the second MAC PDU are same, one of the firstMAC PDU and the second MAC PDU may be selected to be sent according toanother rule, for example, the second MAC PDU is sent, and then theother MAC PDU is reserved, that is, the first MAC PDU is reserved.Contrary to this case, if the HARQ processes of the first MAC PDU andthe second MAC PDU are same, one of them may be selected to be sentaccording to a certain rule, for example, the second MAC PDU is sent,then for the other MAC PDU, that is, the first MAC PDU, the first MACPDU may be flushed.

Optionally, for a case that the configured grant timer corresponding tothe target HARQ process is running, the method 200 may further include:the MAC layer determines that the NDI corresponding to the target HARQprocess is flipped, and/or, the third resource is sent to the HARQentity at the MAC layer. Or, in combination with the third condition,when the configured grant timer corresponding to the target HARQ processis running and the third condition is met, the MAC layer may determinethat the NDI corresponding to the target HARQ process is flipped,and/or, the third resource is sent to the HARQ entity at the MAC layer.Herein, the third condition includes at least one of followingconditions: the first resource and/or the third resource are configuredgrant resources; it is determined there is the untransmitted first MACPDU in the target HARQ process; the first resource corresponding to thefirst MAC PDU which exists in the target HARQ process is nottransmitted; it is determined that the first resource overlaps with thesecond resource; the first TB in the target HARQ process is nottransmitted; the priority of the second resource is higher than thepriority of the first resource; the second resource is transmitted priorto the first resource; the third resource is a preemption resource; theHARQ process number corresponding to the first resource and the HARQprocess number corresponding to the third resource are same.

Or, the third condition may also include: if the HARQ processes of thefirst MAC PDU and the second MAC PDU are same, then in a time order, theformer MAC PDU may be reserved, and the other MAC PDU may be sent.Contrary to this case, if the HARQ processes of the first MAC PDU andthe second MAC PDU are same, then in a time order, the former MAC PDUmay also be flushed and the latter MAC PDU may be sent.

Similarly, the third condition may also include: if the HARQ processesof the first MAC PDU and the second MAC PDU are same, then according toanother rule, one of the first MAC PDU and the second MAC PDU may beselected to be sent, and the other MAC PDU may be reserved. Contrary tothis case, if the HARQ processes of the first MAC PDU and the second MACPDU are same, then according to a certain rule, one of the first MAC PDUand the second MAC PDU may be selected to be sent and the other MAC PDUmay be flushed.

It should be understood that for a case that a condition which may beincluded in the third condition belongs to a condition which may beincluded in the first condition, the above description about the firstcondition is applied, which will not be repeated here for sake ofbrevity.

It should be understood that the third condition may be used togetherwith the first condition, that is, both the first condition and thethird condition are set.

Or, the third condition may also be set separately, that is, only thethird condition is set, and when the third condition is met, the actscorresponding to the third condition are performed. Since the firstcondition is not set, at this time the acts corresponding to the firstcondition may be directly performed, or whether to perform the actscorresponding to the first condition may be determined in another mode.For example, whether to reassemble the first MAC PDU at the MAC layer toobtain the third MAC PDU and send the third MAC PDU is determined inanother mode. Or, in a case that the first condition is not set, theacts corresponding to the first condition may not be performed either.For example, the first condition is not set, and reassembling the firstMAC PDU at the MAC layer to obtain the third MAC PDU is not performedeither.

Or, similarly, the first condition may also be set separately, that is,only the first condition is set, and in a case that the first conditionis met, the acts corresponding to the first condition are performed.Since the third condition is not set, at this time the actscorresponding to the third condition may be directly performed, orwhether to perform the acts corresponding to the third condition may bedetermined in another mode. For example, it is determined in anothermode that the MAC layer determines whether the NDI corresponding to thetarget HARQ process is flipped, and whether to send the third resourceto the HARQ entity at the MAC layer. Or, in a case that the thirdcondition is not set, the acts corresponding to the third condition maynot be performed. For example, if the third condition is not set, atleast one of following is not performed: the MAC layer determineswhether the NDI corresponding to the target HARQ process is flipped, andthe MAC layer sends the third resource to the HARQ entity, but theimplementations of the present disclosure are not limited thereto this.

Optionally, as another implementation, the MAC SDU in the first MAC PDUbeing included in the third MAC PDU may also refer to that the third MACPDU is the first MAC PDU, or the third MAC PDU includes the first MACPDU and a padding bit. Specifically, in a case that the second conditionis met, the terminal device may send the third MAC PDU to the physicallayer at the MAC layer, wherein the third MAC PDU is the first MAC PDU,or the third MAC PDU includes the first MAC PDU and a padding bit.

Herein, the second condition includes at least one of followingconditions: a size of the third resource matches a size of the first MACPDU; according to a first TB in the target HARQ process, it isdetermined that the NDI corresponding to the target HARQ process isflipped, wherein the first TB corresponds to the first resource; thereis the untransmitted first MAC PDU in the target HARQ process; the firstresource corresponding to the first MAC PDU which exists in the targetHARQ process is not transmitted; the first resource overlaps with thesecond resource; indication information sent by the physical layer isreceived at the MAC layer, and the indication information indicates thatthe first MAC PDU in the target HARQ process is not transmitted; thefirst resource and/or the third resource are configured grant resources;the configured grant timer corresponding to the target HARQ process isrunning; the NDI corresponding to the target HARQ process is flipped;the first TB in the target HARQ process is not transmitted; the priorityof the third resource is higher than the priority of the first resource;the third resource is a preemption resource; the priority of the secondresource is higher than the priority of the first resource; the secondresource is transmitted prior to the first resource; the HARQ processnumber corresponding to the first resource and the HARQ process numbercorresponding to the third resource are same.

Or, the second condition may also include: if the HARQ processes of thefirst MAC PDU and the second MAC PDU are same, then in a time order, theformer MAC PDU may be reserved, and the other MAC PDU may be sent.Contrary to this case, if the HARQ processes of the first MAC PDU andthe second MAC PDU are same, then in a time order, the former MAC PDUmay be flushed and the latter MAC PDU may be sent.

Similarly, the second condition may also include: if the HARQ processesof the first MAC PDU and the second MAC PDU are same, one of the firstMAC PDU and the second MAC PDU may also be selected to be sent accordingto another rule, and the other MAC PDU may be reserved. Contrary to thiscase, if the HARQ processes of the first MAC PDU and the second MAC PDUare same, then according to a certain rule, one of the first MAC PDU andthe second MAC PDU may also be selected to be sent and the other MAC PDUmay be flushed.

It should be understood that there is part of conditions in variousconditions which may be included in the second condition that belongs tothe conditions which may be included in the first condition, thus theabove description about the first condition is also applied, which willnot be repeated here for sake of brevity.

Different from the first condition, the second condition may include: ifthe size of the third resource matches the size of the first MAC PDU,then the MAC layer may directly send the first MAC PDU to the physicallayer, such that the physical layer uses the third resource to send thefirst MAC PDU; or, after padding is added to the first MAC PDU, thefirst MAC PDU is sent through the physical layer.

Optionally, similar to the previous implementation, in theimplementation, for the above case that the configured grant timercorresponding to the target HARQ process is running, the method 200 mayalso include: the MAC layer determines that the NDI corresponding to thetarget HARQ process is flipped, and/or, the third resource is sent tothe HARQ entity at the MAC layer. Or, in combination with the thirdcondition, when the configured grant timer corresponding to the targetHARQ process is running and the third condition is met, the MAC layerdetermines that the NDI corresponding to the target HARQ process isflipped, and/or, the third resource is sent to the HARQ entity at theMAC layer.

Herein, for the description about that the condition which may beincluded in the third condition is applicable to the condition which maybe included in the third condition in the previous implementation, whichwill not be repeated here for sake of brevity.

In addition, the third condition and the second condition may also beused in combination or separately. Herein, when the third condition isused alone, the second condition is not set, and correspondingly theacts corresponding to the second condition may be directly performed, orwhether to perform the acts corresponding to the second condition may bedetermined in another mode. For example, the second condition is notset, whether to send the third MAC PDU to the physical layer at the MAClayer is determined in another mode, wherein, the third MAC PDU is thefirst MAC PDU, or the third MAC PDU includes the first MAC PDU and apadding bit. Or, in the case that the second condition is not set, theacts corresponding to the second condition may not be performed either.For example, the second condition is not set, and sending the third MACPDU to the physical layer at the MAC layer is not performed, wherein thethird MAC PDU is the first MAC PDU, or the third MAC PDU includes thefirst MAC PDU and a padding bit.

Similarly, for the case that the second condition is used alone, thethird condition is not set, and correspondingly the acts correspondingto the third condition may be directly performed, or whether to performthe acts corresponding to the third condition may be determined inanother mode. For example, the third condition is not set, it isdetermined that the MAC layer determines whether the NDI correspondingto the target HARQ process is flipped and whether to send the thirdresource to the HARQ entity at the MAC layer is determined in anothermode. Or, in a case that the third condition is not set, the actscorresponding to the third condition may not be performed either. Forexample, if the third condition is not set, at least one of following isnot performed: the MAC layer determines whether the NDI corresponding tothe target HARQ process is flipped, and the MAC layer sends the thirdresource to the HARQ entity, but the implementations of the presentdisclosure are not limited thereto this.

For the above two implementations, description will be given below withexamples with reference to different cases.

For example, for each uplink grant, the HARQ entity will performfollowing acts, wherein the uplink grant may be a configured grantresource or a dynamic scheduling resource.

Act 1, HARQ processes related to a whole grant are determined, and act 2is performed for each determined HARQ process, for example, any case offollowing acts 2 may be performed.

Act 2, if the received grant is scheduled by a PDCCH which is notscrambled by TC-RNTI, a previous TB transmission of this HARQ process iscompared and it is determined that a NDI of the corresponding HARQprocess is flipped. Or, if the received grant is scheduled by a PDCCHscrambled by C-RNTI, and the HARQ buffer of the corresponding process isempty. Or, if the UL grant is received in an RAR. Or, if the UL grant isindicated by the PDCCH scrambled by C-RNTI received in an RAR Window,and the PDCCH successfully completes an RA process triggered by a BeamFailure Recovery (BFR). Or, if the UL grant is part of a configured ULgrant bundle, and according to protocol 6.1.2.3 of TS 38.214 [87], theUL grant may be used for initial transmission, and no MAC PDU has beenacquired for the bundle. It is judged whether at least one of the abovecases or conditions is met, and if yes, continuing to perform act 3.

Act 3, if there is an MAC PDU in Msg3 buffer and the UL grant isacquired from the RAR. Or, if there is an MAC PDU in Msg3 buffer, andthe UL grant is indicated by the PDCCH scrambled by the C-RNTI receivedwithin the RAR Window, and the PDCCH successfully completes the RAprocess triggered by BFR. It is judged whether at least one of the abovecases or conditions is met, and if yes, continuing to perform act 4.

Act 4, acquiring the MAC PDU from the Msg3 buffer. Further, act 4 may becontinually performed: if a size of the UL grant does not match a sizeof the acquired MAC PDU, and if the RA process is successfully completedafter receiving this UL grant, continuing to perform act 5.

Act 5, a Multiplexing and assembly entity is indicated to contain MACsubPDU(s) in the subsequent uplink transmission, wherein the MACsubPDU(s) carries the MAC SDU which is from the acquired MAC PDU; and anreassembled MAC PDU is acquired from the multiplexing and assemblyentity.

Optionally, if neither of the above conditions in act 3 is met, act 6may be continually performed after act 2. Act 6, if there is anassembled MAC PDU in the corresponding HARQ process, but the grantcorresponding to the MAC PDU is not transmitted, and the size of the ULgrant does not match the size of the MAC PDU acquired from theidentified HARQ process, then continuing to perform act 7.

Act 7, the Multiplexing and assembly entity is indicated to contain theMAC subPDU(s) in the subsequent uplink transmission, wherein the MACsubPDU(s) carries the MAC SDU from the acquired MAC PDU; and the MAC PDUis acquired from the multiplexing and assembly entity.

Optionally, the above act 6 may also be replaced with following twocases.

In case 1, act 6, if there is an assembled MAC PDU in the correspondingHARQ process, but the grant corresponding to the MAC PDU is nottransmitted, then continuing to perform act 7.

In this case, the MAC PDU is reassembled regardless of whether the sizeof the resource and the size of the MAC PDU are same. Its advantage liesin consistent processing of all cases, which reduces complexity ofprocessing of a UE.

In case 2, act 6, if there is an assembled MAC PDU in the correspondingHARQ process, but the grant corresponding to the MAC PDU is nottransmitted, and the size of the UL grant does not match the size of theMAC PDU acquired from the identified HARQ process, then continuing toperform act 7.

In case 3, act 6, if there is an assembled MAC PDU in the correspondingHARQ process, but the grant corresponding to the MAC PDU is nottransmitted, and the size of the UL grant matches the size of the MACPDU acquired from the identified HARQ process, then act 7 is replacedby: the acquired MAC PDU is the untransmitted MAC PDU stored in theidentified HARQ process.

In case 2 and case 3, the acquisition of MAC PDU is clearly defined fordifferent cases, which ensures the retransmission of the untransmittedMAC PDU, avoids unnecessary packet loss, and ensures the QoS of servicesas much as possible.

Optionally, if neither of the above act 3 and act 6 is met, in the casethat there is an MAC PDU to be transmitted, the MAC PDU is acquired fromthe multiplexing and assembly entity for transmission;

In addition, as another implementation, for configured grant resources,that is, for each configured grant of each serving cell, if transmissionresources are configured and activated, the MAC entity will performfollowing acts.

Act 1, if a first PUSCH duration of a configured uplink grant and asecond PUSCH duration resource indicated by a PDCCH or an RAR do notoverlap, act 2 is continued to be performed.

Act 2, the HARQ process ID is set as a HARQ process ID associated withthe first PUSCH duration. In addition, act 2 may also further include:if the configured Grant Timer of the corresponding HARQ process is notrunning, act 3 is continued to be performed; or, if the configured GrantTimer of the corresponding HARQ process is running, and there is anassembled MAC PDU in the corresponding HARQ process but the MAC PDU isnot transmitted, at least one of act 3 is continued to be performed.

It is determined that the NDI bit of the corresponding HARQ process isflipped; the configured UL grant and corresponding HARQ information aredelivered to the HARQ entity.

In addition, as another implementation, for a dynamic grant resource, ifthe target HARQ process is a process configured for a configured grantresource or the target HARQ process is the same as that configured for aconfigured grant resource, and if the third condition is met, theconfigured Grant Timer of the corresponding HARQ process is started orrestarted.

Therefore, according to the method for transmitting data of theimplementations of the present disclosure, regarding a scenario wheremultiple grants conflict in time domain, for example, in a case that anMAC entity generates one MAC PDU for each grant, but only one MAC PDU isto be transmitted finally, according to different conditions, it may beselected to reassemble and then send the untransmitted MAC PDU, or todirectly use a new resource for transmission, which solves problems thathow the MAC entity determines the transmission situation of the MAC PDUand determines how to process the MAC PDU, ensuring integrity ofprotocol flow processing, clarifying processing behavior of the UE,avoiding unnecessary packet loss, ensuring QoS of services as much aspossible, and maintaining use experience of services of a UE.

Optionally, in the above method 200, if there is an untransmitted MACPDU in the target HARQ process, the terminal device may use anotherresource to send data in the untransmitted MAC PDU. Contrary to thiscase, the terminal device may also not send the data in the MAC PDU.Specifically, FIG. 5 is a schematic flowchart of another method fortransmitting data 300 according to an implementation of the presentdisclosure. The method 300 may be performed by a terminal device, forexample, the terminal device may be the terminal device shown in FIG. 1.Specifically, the method 300 may be performed by an MAC entity includedin the terminal device, in other words, the method 300 may be performedat an MAC layer of the terminal device. Specifically, as shown in FIG.5, the method 300 includes: 5310, if there is an untransmitted first MACPDU in a target HARQ process, a third MAC PDU is sent to a physicallayer at an MAC layer, wherein the physical layer is used fortransmitting the third MAC PDU through a third resource, wherein a firstresource corresponding to the first MAC PDU overlaps with a secondresource corresponding to a second MAC PDU, a configured grant timercorresponding to the target HARQ process is running, and the third MACPDU does not include data in the first MAC PDU. Further, the third MACPDU does not include an MAC CE in the first MAC PDU.

It should be understood that the first resource, the second resource andthe third resource in the method 300 are the same as those in theabove-mentioned method 200, which will not be repeated here for sake ofbrevity.

It should be understood that if the configured grant timer correspondingto the target HARQ process is running, generally if the first resourceand/or the third resource are configured grant resources, the configuredgrant timer corresponding to the target HARQ process is running, but theimplementations of the present disclosure are not limited thereto.Optionally, similar to the method 200, the method 300 further includes:the first MAC PDU and the second MAC PDU are generated at the MAC layer;the second MAC PDU is sent to the physical layer at the MAC layer,wherein the physical layer is used for transmitting the second MAC PDUthrough a second resource; or, the method 300 may further include: thefirst MAC PDU is sent to the physical layer at the MAC layer, but thephysical layer does not send the first MAC PDU. For sake of brevity,details are not repeated here.

In addition, the method 300 further includes: if the configured granttimer corresponding to the target HARQ process is running, it isdetermined at the MAC layer that a New Data Indication (NDI)corresponding to the target HARQ process is flipped, and/or if theconfigured grant timer corresponding to the target HARQ process isrunning, the third resource is sent to the HARQ entity at the MAC layer,such that the HARQ entity sends the third MAC PDU which does not includethe data in the first MAC PDU through the physical layer.

In addition, in the method 300, the case where the configured GrantTimer corresponds to the HARQ process may not be defined. That is, thetarget HARQ process may be a process different from a HARQ processcalculated with the configured configured Grant. That is, another method300 includes: S310, if there is an untransmitted first MAC PDU in atarget HARQ process, sending a third MAC PDU to a physical layer at anMAC layer, wherein the physical layer is used for transmitting the thirdMAC PDU through a third resource, wherein, a first resourcecorresponding to the first MAC PDU overlaps with a second resourcecorresponding to a second MAC PDU, a configured grant timercorresponding to the target HARQ process is running, and the third MACPDU does not include data in the first MAC PDU. Further, the third MACPDU does not include MAC CE in the first MAC PDU.

In Release 16, there may be multiple types of scenarios where grantsconflict with each other in the time domain. Due to complex scenariosand various solutions, there are cases where the MAC entity generatesone MAC PDU for each grant, but only one MAC PDU is transmitted finally.Moreover, the MAC entity may not know which MAC PDU is transmitted/nottransmitted, at this time how to determine the MAC PDU which isgenerated but not transmitted, and process this MAC PDU are not takeninto consideration in the current protocol. In addition, such conflictsoccur at times, and if this untransmitted MAC PDU is directly discarded,it is very likely to cause a large amount of services that should betransmitted to be discarded, which leads to the problem that the QoS ofthe services cannot be met, which reduces use experience of services ofthe UE. For example, URLLC service 2 is in UM mode, and assembled in theMAC PDU, direct packet discarding causes that the data cannot berecovered, the QoS cannot be met, and survival time cannot be ensured(for example if the former and the latter packets are both lost, thetransmission of services will go wrong. Therefore, the method fortransmitting data of implementations of the present disclosure providesa solution for the above scenarios, for example, which solves problemsthat how the MAC entity determines the transmission situation of the MACPDU and determines how to process the MAC PDU, thereby ensuringintegrity of protocol flow processing, clarifying processing behavior ofthe UE, being able to avoid unnecessary packet loss, ensuring QoS ofservices as much as possible, and maintaining use experience of servicesof the UE.

It should be understood that in various implementations of the presentdisclosure, sequence numbers of the above various processes do not implyan order of execution of the various processes, which should bedetermined by their functions and internal logics, and should notconstitute any limitation on implementation processes of theimplementations of the present disclosure.

In addition, the term “and/or” in this specification describes only anassociation relation for describing associated objects and representsthat three relations may exist. For example, A and/or B may representfollowing three cases: only A exists, both A and B exist, and only Bexists. In addition, the symbol “/” in this document generally indicatesthat objects before and after the symbol “/” have an “or” relation.

The methods for transmitting data according to the implementations ofthe present disclosure is described in detail above with reference toFIG. 1 to FIG. 5. A terminal device according to implementations of thepresent disclosure will be described below with reference to FIG. 6 toFIG. 9.

As shown in FIG. 6, a terminal device 400 according to an implementationof the present disclosure includes: a processing unit 410 and atransceiving unit 420. Specifically, the transceiving unit 420 isconfigured to send a third MAC PDU to a physical layer at an MAC layer,if there is an untransmitted first MAC PDU in a target HARQ process,wherein the physical layer is used for transmitting the third MAC PDUthrough a third resource, wherein, a first resource corresponding to thefirst MAC PDU overlaps with a second resource corresponding to a secondMAC PDU, a configured grant timer corresponding to the target HARQprocess is running, and the third MAC PDU does not include data in thefirst MAC PDU.

Optionally, as an implementation, the processing unit 410 is configuredto generate the first MAC PDU and the second MAC PDU at the MAC layer.The transceiving unit 420 is further configured to send the second MACPDU to the physical layer at the MAC layer, wherein the physical layeris used for transmitting the second MAC PDU through the second resource.

Optionally, as an implementation, the transceiving unit 420 is furtherconfigured to send the first MAC PDU to the physical layer at the MAClayer.

Optionally, as an implementation, data in the first MAC PDU includes anMAC SDU in the first MAC PDU.

Optionally, as an implementation, the processing unit 410 is configuredto obtain the third MAC PDU after the MAC layer reassembles the firstMAC PDU.

Optionally, as an implementation, the processing unit 410 is furtherconfigured to obtain the third MAC PDU, after the MAC layer reassemblesthe first MAC PDU through an MAC multiplexing and assembly entity at theMAC layer.

Optionally, as an implementation, the third MAC PDU includes at leastone MAC subPDU(s), wherein the at least one MAC subPDU(s) includes theMAC SDU in the first MAC PDU.

Optionally, as an implementation, the processing unit 410 is furtherconfigured to obtain the third MAC PDU, after the MAC layer reassemblesthe first MAC PDU if a first condition is met; wherein the firstcondition includes at least one of following conditions: a size of thethird resource does not match a size of the first MAC PDU; according toa first TB in the target HARQ process, it is determined that the NewData Indication (NDI) corresponding to the target HARQ process isflipped, wherein the first TB corresponds to the first resource; it isdetermined that there is the untransmitted first MAC PDU in the targetHARQ process; the first resource corresponding to the first MAC PDUwhich exists in the target HARQ process is not transmitted; it isdetermined that the first resource overlaps with the second resource;the NDI corresponding to the target HARQ process is flipped; the firstTB in the target HARQ process is not transmitted; indication informationsent by the physical layer is received at the MAC layer, wherein theindication information indicates that the first MAC PDU in the targetHARQ process is not transmitted; the first resource and/or the thirdresource are configured grant resources; the configured grant timercorresponding to the target HARQ process is running; a priority of thethird resource is higher than a priority of the first resource; thethird resource is a preemption resource; a priority of the secondresource is higher than the priority of the first resource; the secondresource is transmitted prior to the first resource; the HARQ processnumber corresponding to the first resource and the HARQ process numbercorresponding to the third resource are same.

Optionally, as an implementation, the third MAC PDU is the first MACPDU, or the third MAC PDU includes the first MAC PDU and a padding bit.

Optionally, as an implementation, the transceiving unit 420 isconfigured to send the third MAC PDU to the physical layer at the MAClayer if a second condition is met, wherein the second conditionincludes at least one of following conditions: the size of the thirdresource does not match the size of the first MAC PDU; according to afirst TB in the target HARQ process, it is determined that the NDIcorresponding to the target HARQ process is flipped, wherein the firstTB corresponds to the first resource; it is determined that there is theuntransmitted first MAC PDU in the target HARQ process; the firstresource corresponding to the first MAC PDU which exists in the targetHARQ process is not transmitted; it is determined that the firstresource overlaps with the second resource; indication information sentby the physical layer is received at the MAC layer, wherein theindication information indicates that the first MAC PDU in the targetHARQ process is not transmitted; the first resource and/or the thirdresource are configured grant resources; the configured grant timercorresponding to the target HARQ process is running; the NDIcorresponding to the target HARQ process is flipped; the first TB in thetarget HARQ process is not transmitted; the priority of the thirdresource is higher than the priority of the first resource; the thirdresource is a preemption resource; the priority of the second resourceis higher than the priority of the first resource; the second resourceis transmitted prior to the first resource; the HARQ process numbercorresponding to the first resource and the HARQ process numbercorresponding to the third resource are same.

Optionally, as an implementation, the configured grant timercorresponding to the target HARQ process is running, and the processingunit 410 is configured to determine at the MAC layer that the NDIcorresponding to the target HARQ process is flipped if a third conditionis met, and/or send the third resource to the HARQ entity at the MAClayer.

Herein, the third condition includes at least one of followingconditions: the first resource and/or the third resource are configuredgrant resources; it is determined there is the untransmitted first MACPDU in the target HARQ process; the first resource corresponding to thefirst MAC PDU which exists in the target HARQ process is nottransmitted; it is determined that the first resource overlaps with thesecond resource; the first TB in the target HARQ process is nottransmitted; the priority of the second resource is higher than thepriority of the first resource; the second resource is transmitted priorto the first resource; the priority of the third resource is higher thanthe priority of the first resource; the third resource is a preemptionresource; the HARQ process number corresponding to the first resourceand the HARQ process number corresponding to the third resource aresame.

Optionally, as an implementation, if the NDI corresponding to the targetHARQ process is not flipped, the third MAC PDU is the first MAC PDU.

It should be understood that according to what is described above, theterminal device 400 of the implementation of the present disclosure maycorrespondingly perform the method 200 in the implementations of thepresent disclosure, and the above operations and/or functions and otheroperations and/or functions of various units in the terminal device 400are respectively for realizing corresponding processes of the terminaldevice of the various methods in FIG. 1 to FIG. 4, which will not berepeated here for sake of brevity.

Optionally, the terminal device 400 in the implementation of the presentdisclosure may also be configured to perform following acts.Specifically, the transceiving unit 420 is configured to send a thirdMAC PDU to a physical layer at an MAC layer, if there is theuntransmitted first MAC PDU in the target HARQ process, wherein thephysical layer is used for transmitting the third MAC PDU through athird resource, wherein a first resource corresponding to the first MACPDU overlaps with a second resource corresponding to a second MAC PDU, aconfigured grant timer corresponding to the target HARQ process isrunning, and the third MAC PDU does not include data in the first MACPDU.

Optionally, as an implementation, the first resource and/or the thirdresource are configured grant resources.

Optionally, as an implementation, the processing unit 410 is configuredto generate the first MAC PDU and the second MAC PDU at the MAC layer.The transceiving unit 420 is further configured to send the second MACPDU to the physical layer at the MAC layer, wherein the physical layeris used for transmitting the second MAC PDU through the second resource.

Optionally, as an implementation, the transceiving unit 420 is furtherconfigured to send the first MAC PDU to the physical layer at the MAClayer.

Optionally, as an implementation, the processing unit 410 is configuredto determine at the MAC layer that the New Data Indication (NDI)corresponding to the target HARQ process is flipped, if the configuredgrant timer corresponding to the target HARQ process is running; and/orthe transceiving unit 420 is further configured to send the thirdresource to the HARQ entity at the MAC layer, if the configured granttimer corresponding to the target HARQ process is running.

It should be understood that according to what is described above, theterminal device 400 of the implementation of the present disclosure mayalso corresponds to performing the method 300 in the implementations ofthe present disclosure, and the above operations and/or functions andother operations and/or functions of various units in the terminaldevice 400 are respectively for realizing corresponding processes of theterminal device of the various methods in FIG. 5, which will not berepeated here for sake of brevity.

Therefore, with the terminal device of the implementations of thepresent disclosure, for a scenario where multiple grants conflict in thetime domain, in a case that an MAC entity generates one MAC PDU for eachgrant, but only one MAC PDU is to be transmitted finally, according todifferent conditions, it may be selected to reassemble and then send theuntransmitted MAC PDU, or to directly use a new resource fortransmission, which solves a problem that an MAC entity determines atransmission situation of an MAC PDU and determines how to process theMAC PDU, ensures integrity of protocol flow processing, and clarifiesprocessing behavior of a UE, which can avoid unnecessary packet loss,ensure QoS of a service as much as possible, and maintain use experienceof a service of a UE.

FIG. 7 is a schematic structural diagram of a communication device 500according to an implementation of the present disclosure. Acommunication device 500 shown in FIG. 7 includes a processor 510,wherein the processor 510 may call and run a computer program from amemory to implement the method in the implementation of the presentdisclosure.

Optionally, as shown in FIG. 7, the communication device 500 may furtherinclude a memory 520. Herein, the processor 510 may call and run acomputer program from the memory 520 to implement the method in theimplementation of the present disclosure.

Herein, the memory 520 may be a separate device independent of theprocessor 510 or may be integrated in the processor 510.

Optionally, as shown in FIG. 7, the terminal device 500 may furtherinclude a transceiver 530, and the processor 510 may control thetransceiver 530 to communicate with another device. Specifically,information or data may be sent to another device, or information ordata sent by another device is received.

Herein, the transceiver 530 may include a transmitter and a receiver.The transceiver 530 may also further include antennas, wherein aquantity of the antennas may be one or more.

Optionally, the communication device 500 may specifically be a networkdevice of an implementation of the present disclosure, and thecommunication device 500 may implement the corresponding processesimplemented by the network device in various methods of theimplementations of the present disclosure, which will not be repeatedhere for sake of brevity.

Optionally, the communication device 500 may be specifically a mobileterminal/terminal device of an implementation of the present disclosure,and the communication device 500 may implement the correspondingprocesses implemented by the mobile terminal/terminal device in thevarious methods of the implementations of the present disclosure, whichwill not be repeated here for sake of brevity.

FIG. 8 is a schematic structural diagram of a chip of an implementationof the present disclosure. A chip 600 shown in FIG. 8 includes aprocessor 610, wherein the processor 610 may call and run a computerprogram from a memory to implement the method in the implementation ofthe present disclosure.

Optionally, as shown in FIG. 8, the chip 600 may further include amemory 620. Herein, the processor 610 may call and run a computerprogram from the memory 620 to implement the method in theimplementation of the present disclosure.

Herein the memory 620 may be a separate device independent of theprocessor 610, or may be integrated in the processor 610.

Optionally, the chip 600 may further include an input interface 630.Herein, the processor 610 may control the input interface 630 tocommunicate with another device or chip. Specifically, information ordata sent by another device or chip may be acquired.

Optionally, the chip 600 may further include an output interface 640.Herein, the processor 610 may control the output interface 640 tocommunicate with another device or chip. Specifically, information ordata may be outputted to another device or chip.

Optionally, the chip may be applied to a network device in theimplementation of the present disclosure, and the chip may implement thecorresponding processes implemented by the network device in variousmethods of the implementation of the present disclosure, which will notbe repeated here for sake of brevity.

Optionally, the chip may be applied to a mobile terminal/terminal devicein the implementation of the present disclosure, and the chip mayimplement the corresponding processes implemented by the mobileterminal/terminal device in the various methods of the implementation ofthe present disclosure, which will not be repeated here for sake ofbrevity.

It should be understood that the chip mentioned in the implementation ofthe present disclosure may also be referred to as a system-level chip, asystem chip, a chip system or a system chip-on-chip, etc.

FIG. 9 is a schematic block diagram of a communication system 700according to an implementation of the present disclosure. As shown inFIG. 9, the communication system 700 may include a terminal device 710and a network device 720.

Herein, the terminal device 710 may be configured to implement thecorresponding functions implemented by the terminal device in theabove-mentioned methods, and the network device 720 may be configured toimplement the corresponding functions implemented by the network devicein the above-mentioned methods, which will not be repeated here.

It should be understood that, the processor in the implementations ofthe present disclosure may be an integrated circuit chip having a signalprocessing capability. In an implementation process, the acts of theforegoing method implementations may be accomplished through anintegrated logic circuit of hardware in the processor or instructions ina form of software. The above processor may be a general purposeprocessor, a Digital Signal Processor (DSP), an Application SpecificIntegrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) oranother programmable logic device, discrete gate or transistor logicdevice, or a discrete hardware component. The methods, acts and logicalblock diagrams disclosed in the implementations of the presentdisclosure may be implemented or executed. The general purpose processormay be a microprocessor, or the processor may be any conventionalprocessor or the like. The acts of methods disclosed with reference tothe implementations of the present disclosure may be directly embodiedas being executed and accomplished by a hardware decoding processor, ormay be executed and accomplished by a combination of hardware andsoftware modules in the decoding processor. The software modules may belocated in a storage medium commonly used in the art, such as a randommemory, a flash memory, a read-only memory, a programmable read-onlymemory or an electrically erasable programmable memory, or a register,etc. The storage medium is located in a memory, and the processor readsinformation in the memory and accomplishes the acts of the above methodsin combination with hardware thereof.

It may be understood that, the memory in the implementations of thepresent disclosure may be a volatile memory or a non-volatile memory, ormay include both a volatile memory and a non-volatile memory. Herein,the non-volatile memory may be a Read-Only Memory (ROM), a ProgrammableROM (PROM), an Erasable PROM (EPROM), an Electrically EPROM (EEPROM), ora flash memory. The volatile memory may be a Random Access Memory (RAM),which serves as an external cache. As an exemplary but not limitativedescription, many forms of RAMs are available, for example, a Static RAM(SRAM), a Dynamic RAM (DRAM), a Synchronous DRAM (SDRAM), a Double DataRate SDRAM (DDRSDRAM), an Enhanced SDRAM (ESDRAM), a Synchlink DRAM(SLDRAM), and a Direct Rambus RAM (DR RAM). It should be noted that thememory in the systems and the methods described in this specificationare intended to include, but not limited to, these and any memory ofanother suitable type.

It should be understood that, the foregoing memory is exemplary but notlimitative description. For example, the memory in the implementationsof the present disclosure may also be a static RAM (SRAM), a dynamic RAM(DRAM), a synchronous DRAM (SDRAM), a double data Rate SDRAM (DDRSDRAM), an enhanced SDRAM (ESDRAM), a Synch link DRAM (SLDRAM), or aDirect Rambus RAM (DR RAM), or the like. That is, memories in theimplementations of the present disclosure are intended to include, butnot limited to, these and any memory of another suitable type.

An implementation of the present disclosure further provides a computerreadable storage medium, configured to store a computer program.

Optionally, the computer readable storage medium may be applied in anetwork device in an implementation of the present disclosure, and thecomputer program causes a computer to perform the correspondingprocesses implemented by the network device in various methods of theimplementations of the present disclosure, which will not be repeatedhere for sake of brevity.

Optionally, the computer readable storage medium may be applied in amobile terminal/terminal device in an implementation of the presentdisclosure, and the computer program causes the computer to perform thecorresponding processes implemented by the mobile terminal/terminaldevice in various methods of the implementations of the presentdisclosure, which will not be repeated here for sake of brevity.

An implementation of the present disclosure further provides a computerprogram product, including computer program instructions.

Optionally, the computer program product may be applied in a networkdevice in an implementation of the present disclosure, and the computerprogram instructions cause a computer to perform the correspondingprocesses implemented by the network device in various methods of theimplementations of the present disclosure, which will not be repeatedhere for sake of brevity.

Optionally, the computer program product may be applied in a mobileterminal/terminal device of the implementation of the presentdisclosure, and the computer program instructions cause a computer toperform the corresponding processes implemented by the mobileterminal/terminal device in various methods of the implementations ofthe present disclosure, which will not be repeated here for sake ofbrevity.

An implementation of the present disclosure further provides a computerprogram.

Optionally, the computer program may be applied in a network device ofan implementation of the present disclosure. When the computer programis run on a computer, the computer is caused to perform thecorresponding processes implemented by the network device in variousmethods of the implementations of the present disclosure, which will notbe repeated here for sake of brevity.

Optionally, the computer program may be applied in a mobileterminal/terminal device of an implementation of the present disclosure.When the computer program is run on a computer, the computer is causedto perform the corresponding processes implemented by the mobileterminal/terminal device in various methods of the implementations ofthe present disclosure, which will not be repeated here for sake ofbrevity.

Those of ordinary skills in the art may recognize that the exemplaryelements and algorithm acts described in combination with theimplementations disclosed herein can be implemented in electronichardware, or a combination of computer software and electronic hardware.Whether these functions are performed in hardware or software depends onthe specific application and design constraint conditions of thetechnical solution. Skilled artisans may use different methods toimplement the described functions in respect to each particularapplication, but such implementation should not be considered to bebeyond the scope of the present disclosure.

Those skilled in the art may clearly learn that for convenience andconciseness of description, the specific working processes of thesystems, apparatuses and units described above may refer to thecorresponding processes in the foregoing method implementations, whichwill not be repeated here.

In several implementations according to the present disclosure, itshould be understood that the disclosed systems, apparatuses and methodsmay be implemented in another manner. For example, the apparatusimplementations described above are only illustrative, for example, thedivision of the units is only a logical function division, and there maybe another division manner in an actual implementation, for example,multiple units or components may be combined or integrated into anothersystem, or some features may be ignored or not performed. On the otherhand, the mutual coupling or direct coupling or a communicationconnection shown or discussed may be indirect coupling or acommunication connection through some interfaces, apparatuses or units,and may be in electrical, mechanical or another form.

The unit described as a separate component may or may not be physicallyseparated, and the component shown as a unit may or may not be aphysical unit, i.e., it may be located in one place, or may bedistributed over multiple network units. A part or all of the unitstherein may be selected according to an actual need to achieve thepurpose of solutions of the implementations.

In addition, various functional units in various implementations of thepresent disclosure may be integrated in one processing unit, or thevarious units may be physically present separately, or two or more unitsmay be integrated in one unit.

The functions may be stored in a computer readable storage medium, ifrealized in a form of software functional units and sold or used as aseparate product. Regarding such understanding, the technical solutionof the present disclosure, in essence, or the part contributing to theprior art, or the part of the technical solution, may be embodied in aform of a software product, wherein the computer software product isstored in a storage medium, and includes a number of instructions forcausing a computer device (which may be a personal computer, a server,or a network device, or the like) to perform all or part of the acts ofthe methods described in various implementations of the presentdisclosure. And the foregoing storage medium includes: various kinds ofmedia that may store program codes, such as a USB flash drive, aremovable hard disk, a Read-Only Memory (ROM), a Random Access Memory(RAM), a magnetic disk, or an optical disc, etc.

What are described above are merely specific implementations of thepresent disclosure, but the protection scope of the present disclosureis not limited thereto. Any variation or substitution that may be easilyconceived by a person skilled in the art within the technical scopedisclosed by the present disclosure shall be included within theprotection scope of the present disclosure. Therefore, the protectionscope of the present disclosure shall be determined by the protectionscope of the claims.

What is claimed is:
 1. A method for transmitting data, comprising:sending a third Media Access Control (MAC) Protocol Data Unit (PDU) to aphysical layer at an MAC layer, if there is a first MAC PDU not beingtransmitted in a target Hybrid Automatic Repeat reQuest (HARQ) process,wherein, a first resource corresponding to the first MAC PDU overlapswith another resource, the third MAC PDU comprises data in the first MACPDU, and the physical layer is used for transmitting the third MAC PDUthrough a third resource; wherein that the third MAC PDU comprises datain the first MAC PDU comprises: the third MAC PDU is the first MAC PDU;wherein sending the third MAC PDU to the physical layer at the MAC layercomprises: sending the third MAC PDU to the physical layer at the MAClayer, if a second condition is met, wherein the second conditioncomprises at least one of following conditions: a size of the thirdresource matches a size of the first MAC PDU; according to a first TB inthe target HARQ process, it is determined that a NDI corresponding tothe target HARQ process is flipped, wherein the first TB corresponds tothe first resource; it is determined that there is the first MAC PDU notbeing transmitted in the target HARQ process; the first resource and/orthe third resource are configured grant resources; the second resourceis transmitted prior to the first resource; or a HARQ process numbercorresponding to the first resource and a HARQ process numbercorresponding to the third resource are the same.
 2. The method of claim1, further comprising: generating the first MAC PDU and the second MACPDU at the MAC layer; and sending the second MAC PDU to the physicallayer at the MAC layer, wherein the physical layer is used fortransmitting the second MAC PDU through the second resource.
 3. Themethod of claim 1, further comprising: sending the first MAC PDU to thephysical layer at the MAC layer.
 4. The method of claim 1, wherein thedata in the first MAC PDU comprises an MAC Service Data Unit (SDU) inthe first MAC PDU.
 5. The method of claim 4, further comprising:obtaining the third MAC PDU after the MAC layer reassembles the firstMAC PDU.
 6. The method of claim 5, wherein obtaining the third MAC PDUafter the MAC layer reassembles the first MAC PDU, comprises: obtainingthe third MAC PDU after the MAC layer reassembles the first MAC PDUthrough an MAC multiplexing assembly entity.
 7. The method of claim 6,wherein the third MAC PDU comprises at least one MAC subPDU, wherein theat least one MAC subPDU comprises the MAC SDU in the first MAC PDU. 8.The method of claim 5, wherein obtaining the third MAC PDU after the MAClayer reassembles the first MAC PDU, comprises: obtaining the third MACPDU after the MAC layer reassembles the first MAC PDU, if a firstcondition is met; wherein, the first condition comprises at least one offollowing conditions: a size of the third resource does not match a sizeof the first MAC PDU; according to a first Transport Block (TB) in thetarget HARQ process, it is determined that a New Data Indication (NDI)corresponding to the target HARQ process is flipped, wherein the firstTB corresponds to the first resource; it is determined that there is thefirst MAC PDU not being transmitted in the target HARQ process; thefirst resource corresponding to the first MAC PDU which exists in thetarget HARQ process is not transmitted; it is determined that the firstresource overlaps with the second resource; the NDI corresponding to thetarget HARQ process is flipped; the first TB in the target HARQ processis not transmitted; indication information sent by the physical layer isreceived at the MAC layer, wherein the indication information indicatesthat the first MAC PDU in the target HARQ process is not transmitted;the first resource and/or the third resource are configured grantresources; a configured grant timer corresponding to the target HARQprocess is running; a priority of the third resource is higher than apriority of the first resource; the third resource is a preemptionresource; a priority of the second resource is higher than the priorityof the first resource; the second resource is transmitted prior to thefirst resource; or a HARQ process number corresponding to the firstresource and a HARQ process number corresponding to the third resourceare same.
 9. The method of claim 1, wherein the third resource is aconfigured grant resource.
 10. A terminal device, comprising: aprocessor, a memory, and a transceiver, wherein the memory is configuredfor storing a computer program, the transceiver is configured tocommunicate with another device under control of the processor, and theprocessor is configured for executing the computer program from thememory to: send, through the transceiver, a third Media Access Control(MAC) Protocol Data Unit (PDU) to a physical layer at an MAC layer, ifthere is a first MAC PDU not being transmitted in a target HybridAutomatic Repeat reQuest (HARQ) process, wherein, a first resourcecorresponding to the first MAC PDU overlaps with another resource, thethird MAC PDU comprises data in the first MAC PDU, and the physicallayer is used for transmitting the third MAC PDU through a thirdresource; wherein that the third MAC PDU comprises data in the first MACPDU comprises: the third MAC PDU is the first MAC PDU; wherein theprocessor is further configured for executing the computer program fromthe memory to: send, through the transceiver, the third MAC PDU to thephysical layer at the MAC layer if a second condition is met, whereinthe second condition comprises at least one of following conditions: asize of the third resource matches a size of the first MAC PDU;according to a first TB in the target HARQ process, it is determinedthat a NDI corresponding to the target HARQ process is flipped, whereinthe first TB corresponds to the first resource; it is determined thatthere is the first MAC PDU not being transmitted in the target HARQprocess; the first resource and/or the third resource are configuredgrant resources; the second resource is transmitted prior to the firstresource; or a HARQ process number corresponding to the first resourceand a HARQ process number corresponding to the third resource are thesame.
 11. The terminal device of claim 10, wherein the processor isconfigured for executing the computer program from the memory to:generate the first MAC PDU and the second MAC PDU at the MAC layer; andsend, through the transceiver, the second MAC PDU to the physical layerat the MAC layer, wherein the physical layer is used for transmittingthe second MAC PDU through the second resource.
 12. The terminal deviceof claim 10, wherein the processor is configured for executing thecomputer program from the memory to: send, through the transceiver, thefirst MAC PDU to the physical layer at the MAC layer.
 13. The terminaldevice of claim 10, wherein the data in the first MAC PDU comprises anMAC Service Data Unit (SDU) in the first MAC PDU.
 14. The terminaldevice of claim 13, wherein the processor is configured for executingthe computer program from the memory to: obtain the third MAC PDU afterthe MAC layer reassembles the first MAC PDU.
 15. The terminal device ofclaim 14, wherein the processor is configured for executing the computerprogram from the memory to: obtain the third MAC PDU after the MAC layerreassembles the first MAC PDU through an MAC multiplexing assemblyentity.
 16. The terminal device of claim 14, wherein the third MAC PDUcomprises at least one MAC subPDU, wherein the at least one MAC subPDUcomprises the MAC SDU in the first MAC PDU.
 17. The terminal device ofclaim 14, wherein the processor is configured for executing the computerprogram from the memory to: obtain the third MAC PDU after the MAC layerreassembles the first MAC PDU if a first condition is met; wherein, thefirst condition comprises at least one of following conditions: a sizeof the third resource does not match a size of the first MAC PDU;according to a first Transport Block (TB) in the target HARQ process, itis determined that a New Data Indication (NDI) corresponding to thetarget HARQ process is flipped, wherein the first TB corresponds to thefirst resource; it is determined that there is the first MAC PDU notbeing transmitted in the target HARQ process; the first resourcecorresponding to the first MAC PDU which exists in the target HARQprocess is not transmitted; it is determined that the first resourceoverlaps with the second resource; the NDI corresponding to the targetHARQ process is flipped; the first TB in the target HARQ process is nottransmitted; indication information sent by the physical layer isreceived at the MAC layer, wherein the indication information indicatesthat the first MAC PDU in the target HARQ process is not transmitted;the first resource and/or the third resource are configured grantresources; a configured grant timer corresponding to the target HARQprocess is running; a priority of the third resource is higher than apriority of the first resource; the third resource is a preemptionresource; a priority of the second resource is higher than the priorityof the first resource; the second resource is transmitted prior to thefirst resource; or a HARQ process number corresponding to the firstresource and a HARQ process number corresponding to the third resourceare same.
 18. The terminal device of claim 10, wherein the thirdresource is a configured grant resource.
 19. The terminal device ofclaim 10, wherein the configured grant timer corresponding to the targetHARQ process is running, and the processor is configured for executingthe computer program from the memory to determine at the MAC layer thatthe NDI corresponding to the target HARQ process is flipped, and/or sendthe third resource to a HARQ entity at the MAC layer if a thirdcondition is met, wherein the third condition comprises at least one offollowing conditions: the first resource and/or the third resource areconfigured grant resources; it is determined that there is the first MACPDU not being transmitted in the target HARQ process; the first resourcecorresponding to the first MAC PDU which exists in the target HARQprocess is not transmitted; it is determined that the first resourceoverlaps with the second resource; the first TB in the target HARQprocess is not transmitted; the priority of the second resource ishigher than the priority of the first resource; the second resource istransmitted prior to the first resource; the priority of the thirdresource is higher than the priority of the first resource; the thirdresource is a preemption resource; or a HARQ process numbercorresponding to the first resource and a HARQ process numbercorresponding to the third resource are same.
 20. A non-transitorycomputer readable storage medium, configured to store a computerprogram, wherein the computer program causes a computer to: send a thirdMedia Access Control (MAC) Protocol Data Unit (PDU) to a physical layerat an MAC layer, if there is a first MAC PDU not being transmitted in atarget Hybrid Automatic Repeat reQuest (HARQ) process, wherein, a firstresource corresponding to the first MAC PDU overlaps with anotherresource, the third MAC PDU comprises data in the first MAC PDU, and thephysical layer is used for transmitting the third MAC PDU through athird resource; wherein that the third MAC PDU comprises data in thefirst MAC PDU comprises: the third MAC PDU is the first MAC PDU; whereinthe computer program further causes the computer to: send the third MACPDU to the physical layer at the MAC layer if a second condition is met,wherein the second condition comprises at least one of followingconditions: a size of the third resource matches a size of the first MACPDU; according to a first TB in the target HARQ process, it isdetermined that a NDI corresponding to the target HARQ process isflipped, wherein the first TB corresponds to the first resource; it isdetermined that there is the first MAC PDU not being transmitted in thetarget HARQ process; the first resource and/or the third resource areconfigured grant resources; the second resource is transmitted prior tothe first resource; or a HARQ process number corresponding to the firstresource and a HARQ process number corresponding to the third resourceare the same.